home *** CD-ROM | disk | FTP | other *** search
- Path: informatik.tu-muenchen.de!fischerj
- From: fischerj@informatik.tu-muenchen.de (Juergen "Rally" Fischer)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Demo/game to OS friendly part II
- Date: 17 Jan 1996 18:04:18 GMT
- Organization: Technische Universitaet Muenchen, Germany
- Distribution: world
- Message-ID: <4djdn2$2tk@sunsystem5.informatik.tu-muenchen.de>
- References: <4csu3p$oa6@sunsystem5.informatik.tu-muenchen.de> <4cu1jn$1n7@serpens.rhein.de> <4cv7mb$dn6@sunsystem5.informatik.tu-muenchen.de> <4d0k83$atl@serpens.rhein.de> <4d6am7$i9k@sunsystem5.informatik.tu-muenchen.de> <4ddhou$7qu@serpens.rhein.de> <4deshh$mpj@sunsystem5.informatik.tu-muenchen.de> <4dg16j$ha1@serpens.rhein.de>
- NNTP-Posting-Host: hphalle5.informatik.tu-muenchen.de
- Originator: fischerj@hphalle5.informatik.tu-muenchen.de
-
-
- In article <4dg16j$ha1@serpens.rhein.de>, mlelstv@serpens.rhein.de (Michael van Elst) writes:
- |> fischerj@Informatik.TU-Muenchen.DE (Juergen "Rally" Fischer) writes:
- |>
- |> >Michael van Elst (mlelstv@serpens.rhein.de) wrote:
- |> >: fischerj@informatik.tu-muenchen.de (Juergen "Rally" Fischer) writes:
- |>
- |> >: >aeh :) I mean, the videocontroll just changes bplcon to get it
- |> >: >non-dualpf, but the OS still handles it as dualpf ?
- |>
- |> >: It is still treated as two bitmaps.
- |>
- |> >not by the hardware, I guess ;)
- |>
- |> You have problems with the english language.
-
- This should have been "not displayed in dualpf mode by the hardware".
- But read about my "how many bitmaps got non-dualpf" comment :)
-
- |>
- |> Yes. It is treated as two bitmaps by the hardware, so-called _play-fields_.
- |> These play-fields can be scrolled independently.
-
- Well, when talking about the hardware, it the question how many bitmaps
- are used gets philosphic, as you could interpret a playfield as
- "4 overlayed same-width 1-plane-bitmaps" ;) BTW I know bplcon2 still works
- also in non-dual mode, else I couldn't have written my routine ;)
-
- |>
- |> It is not handled as dual-play-field-mode which would change the
- |> colormapping scheme.
-
- yes. The only reason for dualpf mode on AGA is taking care of the
- spriteprioities.
-
- |>
- |> >: Read the section about dual-playfield screens.
- |>
- |> >It tells there are 2 tmpras chained together, as there is no
- |> >next * I guess I got to just put 2 struc tmpras sequential in mem ?
- |>
- |> You have problems with reading even simple text. The structure is
-
- aeh :) I rather had problems to remember the right structure word.
- rasinfo, yesyes :)
-
- |> called RasInfo. TmpRas is used as temporary storage for some rendering
- |> functions.
- |>
- |> struct RasInfo /* used by callers to and InitDspC() */
-
- InitDsp ? :)
-
- |> {
- |> struct RasInfo *Next; /* used for dualpf */
- |> struct BitMap *BitMap;
- |> WORD RxOffset,RyOffset; /* scroll offsets in this BitMap */
- |> };
- ok.
-
- |>
- |> >the setup doesn't chaging $102 every scanline. the one that would does make
- |> >a blank each 2nd line, you said.
- |>
- |> I said ? Check your brain.
-
- (reading old news...):
-
- >>>
- >also I see no way of poking horiz shift without getting different
- >positions than the defined overscan.
-
- Not for each scanline. You may achieve similar effects with attached
- viewports.
- <<<
-
- not for each scanline ?
-
- >>>
- >wouldn't each 256 color vport be lead by some blank lines with
- >copper defining the colors ?
-
- Not really. You can define that a viewport inherits the colors from
- the previous viewport. However, with the current OS you still get
- at least 1 blank line that you have to hide somehow.
- <<<
-
- 1 blank line ?
-
- how to interpret it ? So is there a OSy way to finally get a copper list
- which is changing 102 each line ?
-
- IF so, then I guess I will need to use loadview() for buffering,
- no Amiga-M :\
- So the OS compliant version will behave more nasty to the user on
- OS3.0, which is the price for it working on 4.0 ?
-
- is there ham emulation on gfx-cards btw. Could I also run a ham8 wb on draco ?
-
- |> >mhm anyway I only need the 8 sprites for the special case: AGA&(PAL|NTSC),
- |> >so after checking I can just rape the sprites.
- |>
- |> No, you can't.
-
- ok, I will have to check for non-mmu, non-fpu, kick 3.0, EC020, PCMCIA port,
- and fastmem at $C00000, short:
-
- char *checkvanilla1200(); /* =:) */
-
- returns "okidoki" on A1200, "careful!" on A4000 and "you damn c0d3r" on A3000 :D
-
- Well the only component that could make my copper routines crash in
- a future AGA machine is "kick 3.0". After displaying a warning I will
- let user select, brave OCS/ECS/AGA users _might_ get more speed instead
- of a crash on OS4.0
-
- |>
- |> --
- |> Michael van Elst
- |>
- |> Internet: mlelstv@serpens.rhein.de
- |> "A potential Snark may lurk in every tree."
- ------------------------------------------------------------------------
- fischerj@Informatik.TU-Muenchen.DE (Juergen "Rally" Fischer) =:)
-
-